Systems and methods for creating a grow cycle

ABSTRACT

Systems and methods for creating a grow cycle are described. One embodiment of a method includes receiving a plant type for providing grow lighting and receiving first data for creating a first grow cycle for a first predetermined period of plant growth, where the first grow cycle includes providing a first wavelength of photon-emitting lighting. In some embodiments, the method includes receiving second data for creating a second grow cycle for a second predetermined period of plant growth, where the second grow cycle includes providing a second wavelength of photon-emitting lighting, determining when the first predetermined period of plant growth begins, and in response to determining that the first predetermined period of plant growth has begun, implementing the first grow cycle. In some embodiments, the method includes determining when the second predetermined period of plant growth begins and, in response to determining that the second predetermined period of plant growth has begun, implementing the second grow cycle.

CROSS REFERENCE

This application claims is a continuation of U.S. application Ser. No.14/832,806, filed Aug. 21, 2015, which claims the benefit of U.S.Provisional Application Ser. No. 62/124,987 filed Jan. 9, 2015, whichare hereby incorporated by reference in their entireties.

TECHNICAL FIELD

Embodiments described herein generally relate to systems and methods forproviding grow lighting and, more specifically, to providing low heatphoton-emitting lighting that provides a plurality of wavelengths toincrease plant growth.

BACKGROUND

Many plants have evolved to grow in certain conditions and, as such,many current grow lights are not capable of growing these types ofplants indoors. As an example, certain plants may only grow in a certainregion of the world. Because other regions of the world have differentconditions, these plants are not easily transported for growingelsewhere. While some plants may successfully grow in pots with theright soil, other plants may require a particular type of lighting inorder to grow.

SUMMARY

Systems and methods for creating a grow cycle are described. Oneembodiment of a method includes receiving a plant type for providinggrow lighting and receiving first data for creating a first grow cyclefor a first predetermined period of plant growth, where the first growcycle includes providing a first wavelength of photon-emitting lighting.In some embodiments, the method includes receiving second data forcreating a second grow cycle for a second predetermined period of plantgrowth, where the second grow cycle includes providing a secondwavelength of photon-emitting lighting, determining when the firstpredetermined period of plant growth begins, and in response todetermining that the first predetermined period of plant growth hasbegun, implementing the first grow cycle. In some embodiments, themethod includes determining when the second predetermined period ofplant growth begins and, in response to determining that the secondpredetermined period of plant growth has begun, implementing the secondgrow cycle.

In another embodiment, a system for creating a grow cycle includes agrow lighting assembly that includes a plurality of low heat lightingelements, where a first lighting element of the plurality of low heatlighting elements outputs a first wavelength of photon-emitting light,and where a second lighting element of the plurality of low heatlighting elements outputs a second wavelength of photon-emitting light.Embodiments of the system may also include a computing device thatstores logic that, when executed by the computing device, causes thesystem to provide a user interface for creating a grow cycle, receive aplant type for the grow lighting assembly to provide grow lighting to aplant, and receive first data for creating a first portion of the growcycle for a first predetermined period of plant growth, where the firstportion of the grow cycle includes providing a first wavelength ofphoton-emitting lighting. In some embodiments, the logic causes thesystem to receive second data for creating a second portion of the growcycle for a second predetermined period of plant growth, where thesecond portion of the grow cycle includes providing a second wavelengthof photon-emitting lighting and implement the grow cycle.

In yet another embodiment, a non-transitory computer-readable mediumstores logic that, when executed by a computing device, causes thecomputing device to provide a user interface for creating a grow cycle,receive a plant type for a grow lighting assembly to provide growlighting to a plant, and receive first data for creating a first portionof the grow cycle for a first predetermined period of plant growth,where the first portion of the grow cycle includes providing a firstwavelength of photon-emitting lighting via a first plurality of low heatlighting elements. In some embodiments, the logic causes the computingdevice to receive second data for creating a second portion of the growcycle for a second predetermined period of plant growth, where thesecond portion of the grow cycle includes providing a second wavelengthof photon-emitting lighting via a second plurality of low heat lightingelements and determine when the first predetermined period of plantgrowth begins. In some embodiments, the logic causes the computingdevice to, in response to determining that the first predeterminedperiod of plant growth has begun, implement the first portion of thegrow cycle. Similarly, in some embodiments, the logic causes thecomputing device to determine when the second predetermined period ofplant growth begins and, in response to determining that the secondpredetermined period of plant growth has begun, implement the secondportion of the grow cycle.

These and additional features provided by the embodiments of the presentdisclosure will be more fully understood in view of the followingdetailed description, in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments set forth in the drawings are illustrative and exemplaryin nature and not intended to limit the disclosure. The followingdetailed description of the illustrative embodiments can be understoodwhen read in conjunction with the following drawings, where likestructure is indicated with like reference numerals and in which:

FIG. 1 depicts a computing environment for providing grow lighting,according to embodiments described herein;

FIG. 2 depicts a grow lighting device, according to embodimentsdescribed herein;

FIG. 3 depicts a user interface for creating a new grow cycle, accordingto embodiments described herein;

FIG. 4 depicts a user interface for providing current grow cycles,according to embodiments described herein;

FIG. 5 depicts a user interface for providing a light tree, according toembodiments described herein;

FIG. 6 depicts a user interface for providing grow cycle details,according to embodiments described herein;

FIG. 7 depicts a user interface for providing performance reports,according to embodiments described herein;

FIG. 8 depicts a user interface for providing administrative settings,according to embodiments described herein;

FIG. 9 depicts a flowchart for providing grow lighting, according toembodiments described herein;

FIG. 10 depicts a flowchart for controlling grow lighting, according toembodiments described herein; and

FIG. 11 depicts a computing infrastructure for providing grow lighting,according to embodiments described herein.

DETAILED DESCRIPTION

Embodiments disclosed herein include systems and methods for providinggrow lighting. Some embodiments may be configured with a lighting devicethat provides a plurality of different lighting wavelengths of growlighting. The grow lighting is configured to emit photons thatfacilitate growth in various plants. Accordingly, embodiments describedherein may be configured to determine a lighting cycle, where thelighting cycle includes a plurality of different lighting wavelengths(such as nanometer-scale wavelengths) emitted at different times. As anexample, a first lighting element (such as a first LED) may provide afirst wavelength of photon-emitting light, and a second lighting element(such as a second LED) may provide a second wavelength ofphoton-emitting light. In some embodiments, the first lighting elementilluminates at a different time than the second lighting element. Thelighting cycle may depend on the particular type of plants being grownand the developmental stage of the plant.

As an example, tomato plants may optimally grow with a firstpredetermined cycle, while basil may grow with a second predeterminedcycle. The first predetermined cycle may include a first wavelength oflight during the initial stages of development to optimize stem growthand a second wavelength of light at later stages of development tooptimize fruit growth. Similarly, some plants may optimally grow withdifferent light wavelengths at different times of day. Accordingly,embodiments described herein may provide a computing infrastructure forcreating and utilizing these cycles for optimizing growth of differentplants in a controlled environment. The systems and methods forproviding grow lighting incorporating the same will be described in moredetail, below.

Referring now to the drawings, FIG. 1 depicts a computing environmentfor providing grow lighting, according to embodiments described herein.As illustrated, the computing environment may include a network 100, agrow lighting assembly 102, a remote computing device 104, and a usercomputing device 106. The network 100 may include any wide area network,such as the internet, a mobile communication network, a public switchtelephone network (PSTN), and the like. Similarly, the network 100 mayinclude a local area network, which may include devices forcommunicating one or more various protocols, such as Ethernet, wirelessfidelity (WiFi), Bluetooth™, near field communication, etc.

The grow lighting assembly 102 may include at least one hub device 108and at least one grow lighting device 110. The hub may include a memorycomponent 140, which stores cycle logic 144 a and lighting logic 144 b.As discussed in more detail below, the grow lighting device 110 mayinclude a low heat lighting element (or a plurality of low heat lightingelements), which may be embodied as a light emitting diode (LED), coldcathode fluorescent lamp (CCFL), and/or other low heat lighting device,so long as the low heat lighting element is configured for outputtingphoton-emitting light to facilitate plant growth. The grow lightingdevice 110 may include a plurality of different LEDs, each of which isspecifically tuned to output a particular wavelength of photon-emittinglight. In operation, the hub device 108 may receive a grow cycle, whichmay be deciphered via the cycle logic 144 a. The lighting logic 144 bmay then facilitate commands of the grow lighting device 110 to providethe desired lighting output for the plants being grown, as described inmore detail below.

Depending on the particular embodiment, the grow lighting assembly 102may include one or more positioning devices for raising and/or loweringthe grow lighting devices 110 relative to the plants being grown.Similarly, watering devices, fertilizing devices, light filteringdevices, light sensing devices, and/or other devices for furtherfacilitating growth of the plants may be included with the grow lightingassembly 102 and may be controlled by the hub device 108, the remotecomputing device 104 and/or the user computing device 106. Depending onthe particular embodiment, one or more sensors (such as a camera,proximity sensor, laser, etc.) may be utilized to determine the heightand/or development of the plant such that the positioning device mayautomatically adjust to provide the desired distance between the growlighting device 110 and the plant. While the grow lighting assembly 102may be configured for outdoor operation, oftentimes, indoor operationmay be desired to fully control lighting and other environmentalconditions for the plants.

Additionally, the remote computing device 104 and the user computingdevice 106 may be configured for providing at least one user interfaceto receive grow cycle cycles from a user, as well as for implementingthe grow cycle for a particular grow lighting assembly 102. In oneembodiment, the user computing device 106 may be utilized by a creatinguser for creating a grow cycle, which is received and stored by theremote computing device 104. The user computing device 106 (and/oranother computing device) may then provide a command for implementingthe grow cycle on the grow lighting assembly 102. The remote computingdevice 104 may then send the cycle to the hub device 108 forimplementation. The hub device may receive the cycle and determine theillumination pattern for implementing the grow cycle. The illuminationpattern may include timing for providing power to one or more of the lowheat lighting elements to achieve the grow cycle.

It should be understood that the embodiment depicted in FIG. 1 is merelyan example. In some embodiments, the hub device 108 may be part of theuser computing device 106. Similarly, some embodiments may be configuredsuch that the user computing device 106 communicates to the hub device108 and the lighting assembly 102 without use of the remote computingdevice 104. Other communication configurations that provide thedescribed functionality are also contemplated.

FIG. 2 depicts a grow lighting device 110, according to embodimentsdescribed herein. As illustrated, the grow lighting device 110 mayinclude circuitry to illuminate a plurality of LEDs 210 a, 210 b, 210 c,210 d, 210 e, 210 f. Depending on the particular embedment, the growlighting device may include a processor, which runs store commands basedon information from the remote computing device 104, the user computingdevice 106, and/or the hub 108. Accordingly, the grow lighting devicemay include software and/or other logic that utilizes wave-basedtechnology for reducing heat and other undesirable bi-products of thelighting device. Also depending on the particular embodiment, the LEDs210 may be the same color or at least a portion of the LEDs 210 may bedifferent colors to provide different photon-emitting lightingwavelengths. As an example, the LEDs 210 a, 210 b may output a redwavelength of light. The LEDs 210 c, 210 d may output a blue wavelength.The LEDs 210 e, 210 f may output a yellow wavelength. Some embodimentsmay be configured with each of the LEDs 210 a different color, and/orwith colors beyond the primary colors, such as warm white, cool white,orange, green, violet, black, etc.

It should be understood that each (or at least a portion) of the LEDs210 may be independent in that they may be illuminated with or withoutother LEDs on the grow lighting device 110. Additionally included is acommunication interface 212, which may take the form of a power cable,an Ethernet cable, and/or other interface for providing power to thegrow lighting device 110, as well as instructions on the lighting cyclefor the grow lighting device 110. In some embodiments, the grow lightingdevice 110 may be hardwired for illumination as instructed by the hubdevice 108. Other embodiments of the grow lighting device 110 may beconfigured with hardware and/or software for receiving an instructionfrom the hub device 108 and controlling illumination of the LEDs.

It should also be understood that by using low heat lighting elements,such as LEDs 210, the photon-emitting light may be produced with littleto no heat. As a consequence, the grow lighting device 110 may bepositioned at a place relative to a plant that maximizes optimal growthwithout the risk of burning the plant with heat from the grow lightingdevice 110. Additionally, cooling of a grow room that includes growlighting devices 110 may be unnecessary because of the minimal amount ofheat produced by the grow lighting devices 110. Additionally, while thegrow lighting device 110 of FIG. 2 is depicted with six LEDs, this isalso an example. Depending on the embodiment, the grow lighting device110 may include as few as one low heat lighting element or as many hashundreds of low heat lighting elements to provide the desiredillumination.

FIG. 3 depicts a user interface 330 for creating a new grow cycle,according to embodiments described herein. As illustrated, the userinterface 330 may be configured for receiving a new grow cycle. The userinterface 330 may include at least one user option, such as a growcycles option 332, a grow cycle details option 334, a light tree option336, an input harvest data option 338, a reports option 340, a messagesoption 342, and a settings option 344. In response to selection of thegrow cycles option 332, a listing of grow cycles to which the user hasaccess may be provided, as described in more detail in FIG. 4. Inresponse to selection of the grow cycle details option 334, additionaldetails regarding one or more of the grow cycles may be provided, asdescribed in more detail in FIG. 6. In response to selection of thelight tree option 336, a depiction of the lighting and plantconfiguration may be provided, as described in more detail in FIG. 5. Inresponse to selection of the input harvest data option 338 dataregarding the progress of the plants may be provided. In someembodiments, the user may input this progress data, while otherembodiments may receive sensor data to monitor this information.

In response to selection of the reports option 340 one or more reportsmay be provided, as described in more detail in FIG. 7. In response toselection of the messages option 342, one or more messages may beprovided. In response to selection of the settings option 344, the usermay be provided with settings for further configuring the grow lightingassembly 102 and/or other components described herein, as described inmore detail in FIG. 8.

Also included are a view option 346 and a start new grow cycle option348. In response to selection of the view option 346, the creating usermay be provided with one or more different user interfaces for showinggrow cycles that may be implemented for different plants, developmentalstages, etc. In response to selection of the start new grow cycle option348, the creating user may be provided with additional options forcreating a new grow cycle.

As an example, the additional options may include a name option tocreate a name for the new grow cycle. Other options may include anoption to identify a number, type, and location of the grow lightingdevices 110. The creating user may additionally provide informationregarding recommended types of plants, a number of plants, and aposition of plants. Options for providing at least one lighting time(such as a first lighting time and a second lighting time) for at leastone of the grow lighting devices 110 to illuminate, as well as providingcycle times for at least one of the grow lighting devices 110 to repeata cycle of illumination of a grow cycle. The cycle time may be set for apredetermined number of minutes, hours, days, weeks, etc. such that thelighting times may change as the plant develops. Accordingly,embodiments may include options for the creating user to select that thelighting scheme changes when it is determined that a plant has reached apredetermined developmental stage. As such, each grow lighting device110 may operate differently, based on the development of those plants.Some embodiments however operate such that at least a portion of thegrow lighting devices 110 provide the same lighting for all plants of acommon variety. Other options may also be provided for creating a growcycle.

Once created, the grow cycle may be listed in the user interface 330(and/or the user interface 430 from FIG. 4, described below). The growcycle may include a name field, a location field, a start date field, acycle field, an end date field, an input harvest field, a light taskfield, and a days until next task field. By selecting a previouslycreated grow cycle, the user (either the creating user or other user)may view and/or amend the selected grow cycle.

FIG. 4 depicts a user interface 430 for providing current grow cycles,according to embodiments described herein. While the user interface 330of FIG. 3 depicted options that are provided when no grow cycles havebeen created, the user interface 430 of FIG. 4 illustrates a pluralityof grow cycles. Specifically, the user interface 430 includes an alertssection 432 and a cycles section 434. The alerts section 432 may beconfigured to provide a notification (e.g., alert and/or message)related to a grow lighting assembly 102, grow lighting device 110, anaction to take for a particular developmental stage of a plant, and/or aplant to which a cycle is being applied. Accordingly, alerts may includea malfunction alert, a pruning reminder, a harvest reminder, a progressalert, a fertilizer reminder, a water reminder, and/or other alerts andmessages. Selection of a details option 436 may provide additionaldetails regarding the provided notifications.

The cycles section 434 may include a listing of cycles to which the usermay be utilizing. These cycles may have been downloaded from arepository that was populated by a creating user who is an expert in thefield of plant growth and/or may be created by any user via selection ofa create new cycle option 438. In response to selection of a detailsoption 440, details regarding a selected cycle may be provided.

FIG. 5 depicts a user interface 530 for providing a light tree,according to embodiments described herein. In response to selection ofthe light tree option 336 from FIG. 3, the user interface 530 may beprovided. As illustrated, the user interface 530 provides a graphicaldepiction of plants and grow lighting devices 110 for a particular growlighting assembly 102. The embodiment of FIG. 5 depicts that basil andtomato are being grown and, in response to selection of one of theplants information regarding the lighting cycle and developmentalprogress of the plant may be provided. In response to selection of oneof the racks, information regarding the grow lighting devices 110 may beprovided.

FIG. 6 depicts a user interface 630 for providing grow cycle details,according to embodiments described herein. In response to selection ofthe grow cycle details option 334 from FIG. 3, the user interface 630may be provided. As illustrated, the user interface 630 may include adetails section 632, which includes a plurality of tasks for a growcycle. Specifically, the details section 632 may include a task field634, a light setting field 636, a days field 638, an on field 640, anoff field 642, a warm white field 644, a cool white field 646, a growblue field 648, a grow red field 650, a total mols field 652, and amessage alert field 654. A save option 656 is also provided, as well asa create option 658.

FIG. 7 depicts a user interface 730 for providing performance reports,according to embodiments described herein. In response to selection ofthe reports option 340 from FIG. 3, the user interface 730 may beprovided. The user interface 730 may include a reports section 732 forproviding performance reports, lighting reports, and/or other reports.The user interface 730 illustrates a tomato cycle performance reportswith a yield statistic that shows the tomato yield for a plant that hasbeen subject to a plurality of cycles.

FIG. 8 depicts a user interface 830 for providing administrativesettings, according to embodiments described herein. In response toselection of the settings option 344 from FIG. 3, the user interface 830may be provided. As illustrated, the user interface 830 may include anupdates option 832, an automation settings option 834, an alertssettings option 836, and a user preferences option 838.

FIG. 9 depicts a flowchart for providing grow lighting, according toembodiments described herein. As illustrated in block 950, a lightingcycle for a predetermined plant type may be received. In block 952, acommand for implementing the lighting cycle with a predetermined growlighting assembly 102 may be received, where the grow lighting assembly102 includes a grow lighting device 110 with a plurality of lightemitting diodes (and/or other low heat lighting elements). In block 954,an illumination pattern for implementing the lighting cycle for the growlighting assembly 102 may be determined. In block 956 the illuminationpattern (or plurality of different illumination patterns) may be sent tothe grow lighting assembly 102 for implementation.

FIG. 10 depicts a flowchart for controlling grow lighting, according toembodiments described herein. As illustrated in block 1050, a plant typefor grow lighting may be received. In block 1052, a first lighting cyclemay be received for a first predetermined period of plant growth, wherethe first lighting cycle includes providing a first wavelength oflighting. In block 1054, a second lighting cycle may be received for asecond predetermined period of plant growth, where the second lightingcycle includes a second wavelength of lighting and is different than thefirst wavelength of lighting. In block 1056, the first lighting cycleand the second lighting cycle are implemented.

FIG. 11 depicts a computing infrastructure for providing grow lighting,according to embodiments described herein. The hub device 108 includes aprocessor 1130, input/output hardware 1132, network interface hardware1134, a data storage component 1136 (which stores cycle data 1138 a,lighting data 1138 b, and/or other data), and the memory component 140.The memory component 140 may be configured as volatile and/ornonvolatile memory and as such, may include random access memory(including SRAM, DRAM, and/or other types of RAM), flash memory, securedigital (SD) memory, registers, compact discs (CD), digital versatilediscs (DVD), and/or other types of non-transitory computer-readablemediums. Depending on the particular embodiment, these non-transitorycomputer-readable mediums may reside within the hub device 108 and/orexternal to the hub device 108.

The memory component 140 may store operating system logic 1142, thecycle logic 144 a and the lighting logic 144 b. The cycle logic 144 aand the lighting logic 144 b may each include a plurality of differentpieces of logic, each of which may be embodied as a computer program ormodule, firmware, and/or hardware, as an example. A local interface 1146is also included in FIG. 11 and may be implemented as a bus or othercommunication interface to facilitate communication among the componentsof the hub device 108.

The processor 1130 may include any processing component operable toreceive and execute instructions (such as from a data storage component1136 and/or the memory component 140). As described above, theinput/output hardware 1132 may include and/or be configured to interfacewith the components of FIG. 11.

The network interface hardware 1134 may include and/or be configured forcommunicating with any wired or wireless networking hardware, includingan antenna, a modem, a LAN port, wireless fidelity (WiFi) card, WiMaxcard, mobile communications hardware, and/or other hardware forcommunicating with other networks and/or devices. From this connection,communication may be facilitated between the hub device 108 and othercomputing devices, such as those depicted in FIG. 1.

The operating system logic 1142 may include an operating system and/orother software for managing components of the hub device 108. Asdiscussed above, the cycle logic 144 a may reside in the memorycomponent 140 and may be configured to cause the processor 1130 todetermine one or more cycles that may be utilized for growing apredetermined plant. Similarly, the lighting logic 144 b may be utilizedto coordinate different grow lighting devices 110 for implementing theappropriate cycle.

It should be understood that while the components in FIG. 11 areillustrated as residing within the hub device 108, this is merely anexample. In some embodiments, one or more of the components may resideexternal to the hub device 108. It should also be understood that, whilethe hub device 108 is illustrated as a single device, this is alsomerely an example. In some embodiments, the cycle logic 144 a and thelighting logic 144 b may reside on different computing devices. Asanother example, one or more of the functionalities and/or componentsdescribed herein may be provided by the remote computing device 104, theuser computing device 106, the lighting assembly 102, and/or othercomputing devices, which may be coupled to the hub device 108 via thenetwork 100. These computing devices may also include hardware and/orsoftware for performing the functionality described herein.

Additionally, while the hub device 108 is illustrated with the cyclelogic 144 a and the lighting logic 144 b as separate logical components,this is also an example. In some embodiments, a single piece of logicmay cause the hub to provide the described functionality.

As illustrated above, various embodiments for providing grow lightingare disclosed. As the grow lighting may be configured for programming ofdifferent wavelength light that provides different photons to the plantsat different stages of development, plant growth may be optimized.Additionally, by utilizing LED or other low heat devices, the positionof the grow lighting may be optimized based on the lighting needs of theplants.

While particular embodiments and aspects of the present disclosure havebeen illustrated and described herein, various other changes andmodifications can be made without departing from the spirit and scope ofthe disclosure. Moreover, although various aspects have been describedherein, such aspects need not be utilized in combination. Accordingly,it is therefore intended that the appended claims cover all such changesand modifications that are within the scope of the embodiments shown anddescribed herein.

It should now be understood that embodiments disclosed herein includessystems, methods, and non-transitory computer-readable mediums forproviding grow lighting. It should also be understood that theseembodiments are merely exemplary and are not intended to limit the scopeof this disclosure.

What is claimed is:
 1. A system for creating a grow cycle to growplants, comprising: a grow lighting assembly that comprises a pluralityof low heat lighting elements; and a computing device that stores logicthat, when executed by the computing device, causes the system toperform at least the following: provide a first user interface forcreating a grow cycle, wherein the first user interface provides a useroption for creating the grow cycle, wherein the first user interface isconfigured for a user, in response to a user selection of the useroption, to design the grow cycle, wherein, creating the grow cycleincludes receiving from the user: a number of low heat lighting elementsthat are actuated, a location of at least a portion of the plurality oflow heat lighting elements that are actuated, a timing of actuation ofat least a portion of the plurality of low heat lighting elements, atype of at least one plant received by the grow lighting assembly, arecommended type of plants for the grow cycle, and a position of the atleast one plant received by the grow lighting assembly; provide a seconduser interface for providing a light tree, which includes a graphicaldepiction of the plants and at least a portion of the plurality of lowheat lighting elements; and implement the grow cycle.
 2. The system ofclaim 1, wherein the grow lighting assembly comprises a sensor thatincludes at least one of the following: a camera, proximity sensor, orlaser.
 3. The system of claim 2, wherein implementing the grow cycleincludes implementing at least one of the following: a malfunctionalert, a pruning reminder, a harvest reminder, a progress alert, afertilizer reminder, or a water reminder, based on information receivedfrom the sensor.
 4. The system of claim 1, wherein the logic furthercauses the computing device to provide an input harvest data option. 5.The system of claim 1, wherein the grow lighting assembly comprises apositioning device for adjusting a position of the plurality of low heatlighting elements according to the grow cycle.
 6. The system of claim 1,wherein implementing the grow cycle includes at least one of thefollowing: receiving a number of plants that will be grown under thegrow cycle, receiving a location of grow lighting devices that will besubject to the grow cycle, receiving a type of grow lighting device thatwill be subject to the grow cycle, or receiving a position of plantsthat will be subject to the grow cycle.
 7. The system of claim 1,wherein the logic further causes the system to provide a statisticassociated with at least one of the following: at least a portion of theplants that are subjected to the grow cycle or the grow lightingassembly.
 8. A non-transitory computer-readable medium for creating agrow cycle for a grow lighting assembly to grow plants that stores logicthat, when executed by a computing device, causes the computing deviceto perform at least the following: provide a first user interface forcreating a grow cycle, wherein the first user interface provides a useroption for creating the grow cycle, wherein the first user interface isconfigured for a user, in response to a user selection of the useroption, to design the grow cycle, wherein, creating the grow cycleincludes receiving the following from the user: a number of low heatlighting elements of the grow lighting assembly that are actuated by thegrow cycle, a location of a at least one of the low heat lightingelements that are actuated by the grow cycle, a timing of actuation ofthe low heat lighting element, a type of the at least one plant receivedby the grow lighting assembly, a recommended type of plants for the growcycle, or a position of the at least one plant received by the growlighting assembly, provide a second user interface for providing a lighttree, which includes a graphical depiction of the plants and the lowheat lighting element; and implement the grow cycle.
 9. Thenon-transitory computer-readable medium of claim 8, wherein the growlighting assembly comprises a sensor that includes at least one of thefollowing: a camera, proximity sensor, or laser.
 10. The non-transitorycomputer-readable medium of claim 9, wherein implementing the grow cycleincludes implementing at least one of the following: a malfunctionalert, a pruning reminder, a harvest reminder, a progress alert, afertilizer reminder, or a water reminder, based on data received fromthe sensor.
 11. The non-transitory computer-readable medium of claim 8,wherein the grow lighting assembly comprises a positioning device foradjusting a position of the low heat lighting element according to thegrow cycle.
 12. The non-transitory computer-readable medium of claim 8,wherein implementing the grow cycle includes at least one of thefollowing: receiving a number of plants that will be grown under thegrow cycle, receiving a location of grow lighting devices that will besubject to the grow cycle, receiving a type of grow lighting device thatwill be subject to the grow cycle, or receiving a position of at least aportion of the plants that are subject to the grow cycle.
 13. Thenon-transitory computer-readable medium of claim 8, wherein the logicfurther causes the computing device to provide a statistic associatedwith at least one of the following: at least a portion of the plantsthat are subjected to the grow cycle or the grow lighting assembly. 14.A grow lighting assembly for creating a grow cycle to grow plants,comprising: a plurality of low heat lighting elements; and a computingdevice that stores logic that, when executed by the computing device,causes the grow lighting assembly to perform at least the following:provide a first user interface for creating a grow cycle, wherein thefirst user interface provides a user option for creating the grow cycle,wherein the first user interface is configured for a user, in responseto a user selection of the user option, to design the grow cycle,wherein, creating the grow cycle includes receiving from the user: anumber of low heat lighting elements of the grow lighting assembly thatare actuated, a location of at least one of the plurality of low heatlighting elements that are actuated, a timing of actuation of the atleast one of the plurality of low heat lighting elements, a type of theat least one plant received by the grow lighting assembly, a recommendedtype of plants for the grow cycle, and a position of the at least oneplant received by the grow lighting assembly; provide a second userinterface for providing a light tree, which includes a graphicaldepiction of the plants and at least a portion of the plurality of lowheat lighting elements; and implement the grow cycle.
 15. The growlighting assembly of claim 14, further comprising at least one of thefollowing: a camera, proximity sensor, or laser.
 16. The grow lightingassembly of claim 15, wherein implementing the grow cycle includesimplementing at least one of the following: a malfunction alert, apruning reminder, a harvest reminder, a progress alert, a fertilizerreminder, or a water reminder.
 17. The grow lighting assembly of claim14, wherein the logic further causes the computing device to provide aninput harvest data option.
 18. The grow lighting assembly of claim 14,wherein the grow lighting assembly comprises a positioning device foradjusting a position of the plurality of low heat lighting elementsaccording to the grow cycle.
 19. The grow lighting assembly of claim 14,further comprising a positioning device for adjusting a position of theplurality of low heat lighting elements according to the grow cycle. 20.The grow lighting assembly of claim 14, wherein implementing the growcycle includes at least one of the following: receiving a number ofplants that will be grown under the grow cycle, receiving a location ofgrow lighting devices that will be subject to the grow cycle, receivinga type of grow lighting device that will be subject to the grow cycle,or receiving a position of at least a portion of the plants that aresubjected to the grow cycle.